home *** CD-ROM | disk | FTP | other *** search
- IMPORTANT NOTE: the filesystem format has changed slightly. To convert to the
- new format run fsck on all your partitions. This will convert symbolic links
- to the new mode and change the magic number of increment 2 V1 filsystems. If you
- don't do this symbolic links wont be recognised. The changes mean symlinks and
- the V1+2 filesystems wont be recognised by earlier versions of Minixfs after
- fsck has finished, hopefully that wont matter.
-
- This version has added a '-e' flag to minit and fsck. If you supply this flag
- it checks the partition size by reading as far as it can before the driver
- software stops it. With some driver software this will give exactly the same
- value as normal, with others '-e' will give a correct value if the boot sector
- has been messed with (e.g. ICD). If you try '-e' on the last partition of a
- hard disk and errors start to be reported, click on Cancel. This means your boot
- sector is probably corrupted (or shows the partition is too large), after a few
- clicks the correct partition size will be shown.
-
- Minit now does a sanity check by comparing the real first sector of a partition
- with what it thinks is the first sector. This should trap any possible problems
- when the driver sofware screws up physical mode.
-
- I've had reports that Minixfs doesn't like '030 based machines (Falcon/TT) and
- Multitos AES. This problem manifests itself as a filesytem crash after a short
- period of use. This is caused by the MiNT+Multitos combination objecting to the
- prescence of the update daemon (presumably due to a bug). If you are using MiNT
- 1.10 (which is only available to the MiNT mailing list at present) then you
- should apply the addroottimeout() patch and Minixfs will happily use
- addroottimeout() and never start the update daemon. It has been reported that
- with this fix Minixfs works happily under Falcons/TT's and MultiTOS. The next
- general MiNT source distribution should include this fix as standard.
-
- A very dirty workaround is to not use Turbo mode, this will however slow down
- the filesystem considerably.
-
- A note to people developing Atari Linux, I've included some patches in this
- version which should make things more compatible. Specifically symbolic links
- use the right mode now and set up their length correctly. Also the V1 filesystem
- uses the alternate form with 30 character filenames. V1 filesystems with a
- directory increment of 1 or 2 should work with 68K Linux now, V2 filesystems
- are not supported 'officially' by Linux. fsck will patch a filesystem to make
- the necessary changes.
-
- A word of warning however! Linux and Minixfs are still incompatible in some
- ways. If you create or copy a Linux partition make sure it doesn't wipe out
- the boot sector of the partition. The partition should be of type GEM unless
- you are using an XHDI >= 1.10 in which case MIX or RAW are also acceptable (and
- you can trash the boot sector too!). The bitmap formats are currently
- incompatible! This means you shouldn't write to Minixfs partitions with Linux
- or vice versa before running the native fsck. In other words if you want to use
- a Minixfs partition with Linux run *Linux* fsck before writing to it. If you
- then want to use the same partition with Minixfs again then run *Minixfs* fsck
- before writing to it. fsck should of course be allowed to 'fix' the bitmap
- 'errors' in each case. The reason I'm not changing the Minixfs bitmap format
- is because this is the format Minix uses and big endian Linux is at fault
- (specifically it treats bitmaps as 32 bit arrays and Minix/Minixfs use only 16
- bit arrays, this is done on PC-Linux too but there is no incompatability
- because it is a little endian machine).
-
- Let me know of any further incompatabilities.
-